home *** CD-ROM | disk | FTP | other *** search
- May 4, 1993.
-
- UUBatchDecoder v1.51 by Fletcher Cocquyt (fletcher@cs.ualberta.ca)
-
-
- Motivation:
-
- Tired of manually editing multi-parted uuencoded files, I
- decided to write this program to do all the drudgery for me.
-
- What does it do?
-
- decode takes two arguments, a source directory and destination
- directory and uudecodes the uuencoded files in the source dir
- to the destination dir.
-
- How does it do that?
-
- In short, decode uses the Usenet Header format to decide which
- uuencoded parts belong to which uudecoded files. It considers
- every file in the source dir with a "Subject" line to be a
- possible uuencoded file. For the articles in the alt.binaries.
- newsgroups, which follow the "standard" header format, decode
- has no problems decoding multiple part binaries, even when
- they are in jumbled order (something most newsreaders won't
- handle).
-
- Syntax:
-
- decode [<source path> <destination path>]
-
- TODO:
-
- Make a much enhanced version with GUI using MUI
- (that's: Graphical User Interface using Stefan Stuntz's
- soon to be released Magical User Interface -
- check out his demo release it looks/works great!)
-
- DISCLAIMER:
-
- I make no guarantee about the function of decode, and
- as such can not be held responsible for any damages
- possibly attributable to its use.
-
- Acknowledgements:
-
- o uudecode source was taken from uudecode.c last
- modified by R.W.Bowers on 88-01-25.
-
- o directory scan routine is based on example8.c in the
- AmigaDOS chapter of Anders Bjerin's ACM System v1.10
-
- o thanks to Tom Warkentin for supplying many uuencoded
- files with which to test this program!
-
-
- History:
-
- 1.51: May 4, 1993:
-
- Improved the file buffering to prevent memory fragmentation.
- CTRL-c is disabled during decoding. Added quit option.
- First released version!
-
- 1.5: Jan 22, 1993:
-
- Implemented file buffering. Now only 32K is used to read in
- the source files. This allows decoding of any sized files.
- 500 lines are read in and decoded at a time.
-
- New improvement: decode now will match subjects more
- intelligently, making sure its matching string is more
- than 2 characters long. Some series have Subject lines like:
- Subject: - Kathy3.gif - SI 1993 Calendar (1/7) FEMALE
- and the '-' would confuse decode when there was more than
- one series with such a '-' right after the Subject:.
- Now decode will look at the next word in the line.
- (This is largely untested, so I may have to revise this
- if problems arise later).
-
- 1.41: Jan 10, 1993:
-
- Totally clean memory allocation/deallocation.
- Have not had any bugs with this version (yet).
- The maximum file size is 65K, I plan to make this
- dynamic later.
-
- 1.4: Jan 7, 1993:
-
- minor bug fixed where decode could mistake the "Message"
- line in the header for the first uuencoded line if it
- was the right number of bytes long.
-
- MAJOR efficiency increase achieved by loading whole
- files into memory for faster decoding.
- (I no longer recommend decoding from ram: to ram: since it
- won't be any faster in the decoding stage).
-
-
- 1.3: Jan 4, 1993:
-
- decode now ignores duplicate files.
- This annoyance was brought to my attention by Tom Warkentin,
- since sometimes a file will be posted twice and it confuses
- decode. Not anymore!
-
- bug fixed where if no begin line was found the output stream
- would miss being closed and when the next output was opened
- caboom! ;) No more!
-
- 1.2: Jan 3, 1993:
-
- decode now ignores part 0's which are common in newsgroups.
- Part zeros used to be taken as the first file to be decoded.
- Now the lowest part number considered is 1.
-
- 1.1 Jan 2, 1993:
-
- decode is now "smart", scanning the source dir for what it
- considers uuencoded files and arranging them in what it
- thinks is the correct order based on the message subject
- line. Many situations are left to be encountered. I
- expect many revisions!
-
- Address:
-
- Internet: fletcher@cs.ualberta.ca
-
-
- Shareware Perpetuation:
-
- If you feel as though the author of this program, (or another)
-
- has saved you hours of tedious work by using his own expertise,
-
- why not consider registering his/her application. This will
-
- (at least) give the "software engineer" in question a sense
-
- of accomplishment and help perpetuate the development of more
-
- innovative, time-saving applications.
-
-
- Sincerely,
-
- Fletcher Cocquyt
- (fletcher@cs.ualberta.ca)
-